Skip to content

[luv-17] Replace multi-slash-command injection with CLI flags and bump to 0.0.8 - #14

Merged
NiveditJain merged 1 commit into
mainfrom
luv-17
Apr 24, 2026
Merged

[luv-17] Replace multi-slash-command injection with CLI flags and bump to 0.0.8#14
NiveditJain merged 1 commit into
mainfrom
luv-17

Conversation

@NiveditJain

Copy link
Copy Markdown
Member

Summary

  • Replace /remote-control with the --remote-control CLI flag and /plan <prompt> with --permission-mode plan + positional prompt, fixing the broken newline-joined injection that produced Invalid color "cyan\n/remote-control".
  • Keep /color <random> only when no user prompt is supplied (no CLI equivalent exists for prompt-bar color, and the single positional slot can't carry both a /color slash command and a user prompt).
  • Bump version to 0.0.8.

Test plan

  • luv <repo> <existing-number> (no prompt): Claude opens in bypassPermissions with a random prompt-bar color and Remote Control active.
  • luv <repo> "fix the auth bug" (with prompt): Claude opens in plan mode, first message is the prompt, Remote Control active, default color (expected trade-off).
  • Docker path: repeat with a repo that has .luv/settings.json + compose_file; confirm docker compose exec passes the same flags.
  • No "Invalid color" error; no /remote-control or /plan text appears as a literal first user message.

🤖 Generated with Claude Code

…p to 0.0.8

The launch prefix joined /color, /remote-control, and /plan with newlines, but
claude treats the positional prompt as one message — when it starts with '/',
the rest (including newlines) becomes the first command's argument, so only
/color ran and the color name was "cyan\n/remote-control". Swap to native CLI
flags: --remote-control replaces the slash command, --permission-mode plan +
positional prompt replaces /plan <prompt>. /color stays only in the no-prompt
branch since it has no flag equivalent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Apr 24, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@NiveditJain has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 41 minutes and 31 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 41 minutes and 31 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: febcdca3-d5a6-4137-a499-d682cdda9a5f

📥 Commits

Reviewing files that changed from the base of the PR and between 71f5581 and 8bb2ddb.

📒 Files selected for processing (2)
  • luv/__init__.py
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch luv-17

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@NiveditJain
NiveditJain merged commit 67d2430 into main Apr 24, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant